-
Couldn't load subscription status.
- Fork 13.9k
Rollup of 6 pull requests #111392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 6 pull requests #111392
Conversation
For some reason, the called function is `cleanup` on LLVM 17 instead of `filter`. r? @Amanieu
…r=m-ou-se Stabilize const_ptr_read Stabilizes const_ptr_read, with tracking issue rust-lang#80377
Limit lifetime of format_args!() with inlined args. Fixes rust-lang#110769
Move some tests r? `@petrochenkov`
…t_config, r=albertlarsan68 support set `rpath` option for each target independently Currently the `rpath` option is a global config and it's effect on all targets. But sometimes when developers edit the rustc code and try to release rust toolchains themselves, they may not want to add `rpath` in all targets to avoid dynamically linked shared object library privilege escalation attack. This PR supports set `rpath` option for each target independently . Common developers are not aware of the existence of this configuration option and do not affect the existing development process. This configuration option takes effect only after developers explicitly sets . r? `@albertlarsan68`
…r=workingjubilee Remove some `assume`s from slice iterators that don't do anything Because the start pointer is iterators is already a `NonNull`, we emit the appropriate `!nonnull` metadata when loading the pointer to tell LLVM that it's non-null. Probably the best way to see that it's the metadata that's important (and not the `assume`) is to observe that LLVM actually *removes* the `assume` from the optimized IR: <https://rust.godbolt.org/z/KhE6G963n>. (I also checked that, yes, the if-not-ZST `assume` on `end` is still doing something: it's how there's a `!nonnull` metadata on its load, even though it's an ordinary raw pointer. The codegen test added in this PR fails if the other `assume` is removed.)
vec-shrink-panik: update expectations to work on LLVM 17 For some reason, the called function is `cleanup` on LLVM 17 instead of `filter`. r? `@Amanieu`
|
@bors r+ rollup=never p=6 |
|
🌲 The tree is currently closed for pull requests below priority 1000. This pull request will be tested once the tree is reopened. |
|
@bors treeclosed-- |
|
@bors treeclosed- |
|
⌛ Testing commit 2e54ec5 with merge f3bd9835f41da7e6e52c9764922a1c9ded4557ec... |
|
The job Click to see the possible cause of the failure (guessed by this bot) |
|
💔 Test failed - checks-actions |
Successful merges:
rpathoption for each target independently #111242 (support setrpathoption for each target independently)assumes from slice iterators that don't do anything #111282 (Remove someassumes from slice iterators that don't do anything)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup